Compilation Memory Report

Execution Memory Report

Compilation Report

Execution Report

Some good compilation time improvements here for such a small change but the memory reports are broken

Interesting, thought rust had quite a good allocator

FWIW I tried the profiling I do with Instruments in #7053 and it seems to have bombed (I'm on Mac):

Or I'm not sure what happens exactly, usually it runs for minutes, and the 12GB is also not something I have seen before.

If I un e.g. info I do see output though 🤷
Maybe the profiler could not attach itself and the compilation stayed fast, but the reported memory completely bogus.

But no, even that's not true, I have stack trace:

It just shows way more memory than expected.

Yeah, heaptrack reports that it doesn't work with custom allocators so we may need to replace this tooling for something else if we go forwards with this.

@ludamad Rust just uses the default system allocator

Looks like valgrind's massif tool isn't working either

Profiling with MIMALLOC_SHOW_STATS=1 I also see the 12GB peak usage. Switching this PR to try out TCMalloc instead

This could be something to continue looking into for the future but I currently can't seem to profile memory usage of jemalloc, and any alternate allocator in general would break our CI so I'm closing this for now despite the possible performance gains.